You can also save a file at any time by right clicking on the Console window.
A "running total" of the more serious errors are written to debugLogs\ErrorLog.txt as well as the console log.
If Crew Chief runs but isn't working for you then the most important thing is to upload the log file that was saved after you saw a problem to either the forum, Discord or to the confidential email address
If that doesn't help then collecting a "repro trace" of all the things Crew Chief does will give more information. To do this:
Open the Run prompt (Win+R) then type:
"%ProgramFiles(x86)%\Britton IT Ltd\CrewChiefV4\CrewChiefV4" -DEBUG
or open a Command Prompt (by typing cmd in start menu) then type:
cd /d "%ProgramFiles(x86)%\Britton IT Ltd\CrewChiefV4"
CrewChiefV4 -DEBUG
Either way Crew Chief should now be running in debug mode:
- Make sure Record checkbox is checked.
- Start CC for your game, and reproduce your problem.
- When you're done, click Stop and Save trace button in CC, and wait for trace write to finish (you'll see a message).
- Two files will be produced: .cct and .txt. In your Documents folder you'll find file looking like CrewChiefV4\debugLogs\[GAME]_2017-12-7--18-30-35.cct and [GAME]_2017-12-7--18-30-35.txt
- Zip
both files and upload to the confidential email address above
- Or upload your favorite web sharing service and send us the link to upload in your post (with problem description).
If Crew Chief crashes you can help by collecting a "boot trace".
Open the Run prompt (Win+R) then type:
"%ProgramFiles(x86)%\Britton IT Ltd\CrewChiefV4\CrewChiefV4" -DEBUG > c:\temp\output.txt 2>&1
or open a Command Prompt (by typing cmd in start menu) then type:
cd /d "%ProgramFiles(x86)%\Britton IT Ltd\CrewChiefV4"
CrewChiefV4 -DEBUG > c:\temp\output.txt 2>&1
Then c:\temp\output.txt contains the messages which can be used by the dev team. The console log file won't be saved but a previous one may help.